Skip to content

Add duplicate detection tip to 'Creating an issue' docs#44816

Merged
Sharra-writes merged 1 commit into
github:mainfrom
sunnyi101:sunnyi101/duplicate-detection-docs
Jun 19, 2026
Merged

Add duplicate detection tip to 'Creating an issue' docs#44816
Sharra-writes merged 1 commit into
github:mainfrom
sunnyi101:sunnyi101/duplicate-detection-docs

Conversation

@sunnyi101

Copy link
Copy Markdown
Contributor

What this PR does

Adds a tip callout to the Creating an issue page explaining the duplicate detection feature.

When creating an issue, GitHub now surfaces potential duplicate issues inline once the title is filled out and the body reaches 100 characters. Up to three existing issues may be suggested. The suggestions are non-blocking and don't prevent issue submission.

Why

This feature is shipping to GA and the docs should reflect the new behavior so users understand what the suggestions are and when they appear.

Context

When creating an issue, GitHub now surfaces potential duplicate issues
inline once the title is filled out and the body reaches 100 characters.
This update adds a tip callout to the 'Creating an issue from a repository'
section explaining the behavior.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot AI review requested due to automatic review settings June 18, 2026 20:15
@welcome

welcome Bot commented Jun 18, 2026

Copy link
Copy Markdown

Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

@github-actions github-actions Bot added the triage Do not begin working on this issue until triaged by the team label Jun 18, 2026
@github-actions

Copy link
Copy Markdown
Contributor

How to review these changes 👓

Thank you for your contribution. To review these changes, choose one of the following options:

A Hubber will need to deploy your changes internally to review.

Table of review links

Note: Please update the URL for your staging server or codespace.

The table shows the files in the content directory that were changed in this pull request. This helps you review your changes on a staging server. Changes to the data directory are not included in this table.

Source Review Production What Changed
issues/tracking-your-work-with-issues/using-issues/creating-an-issue.md fpt
ghec
ghes@ 3.21 3.20 3.19 3.18 3.17
fpt
ghec
ghes@ 3.21 3.20 3.19 3.18 3.17

Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server

🤖 This comment is automatically generated.

@sunnyi101 sunnyi101 left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

pleaser review

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds documentation for the inline duplicate-issue suggestions shown during issue creation, helping users understand when suggestions appear and that they don’t block submission.

Changes:

  • Adds a new tip callout describing duplicate-issue suggestions during issue creation.
  • Gates the tip to {% data variables.product.prodname_dotcom_the_website %}/{% data variables.product.prodname_ghe_cloud %} via {% ifversion fpt or ghec %}.
Show a summary per file
File Description
content/issues/tracking-your-work-with-issues/using-issues/creating-an-issue.md Adds a new tip explaining duplicate-issue suggestion behavior during issue creation.

Copilot's findings

  • Files reviewed: 1/1 changed files
  • Comments generated: 1

@Sharra-writes Sharra-writes added this pull request to the merge queue Jun 19, 2026
Merged via the queue into github:main with commit 76b4352 Jun 19, 2026
50 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

triage Do not begin working on this issue until triaged by the team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants